Nitric Oxide Delivery Device

ABSTRACT

A nitric oxide delivery device including a valve assembly, a control module and a gas delivery mechanism is described. An exemplary gas delivery device includes a valve assembly with a valve and circuit including a memory, a processor and a transceiver in communication with the memory. The memory may include gas data such as gas identification, gas expiration and gas concentration. The transceiver on the circuit of the valve assembly may send wireless optical line-of-sight signals to communicate the gas data to a control module. Exemplary gas delivery mechanisms include a ventilator and a breathing circuit. Methods of administering gases containing nitric oxide are also described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part application of U.S. patentapplication Ser. No. 13/509,873 filed on May 15, 2012, which is theNational Phase entry of PCT/US2011/020319, filed Jan. 6, 2011, theentire content of which are incorporated herein by reference in theirentirety.

TECHNICAL FIELD

Embodiments of the present invention relate to gas delivery device foruse in a gas delivery system for administering therapy gas and methodsof administering therapy gas.

BACKGROUND

Certain medical treatments include the use of gases that are inhaled bythe patient. Gas delivery devices are often utilized by hospitals todeliver the necessary gas to patients in need. It is important whenadministering gas therapy to these patients to verify the correct typeof gas and the correct concentration are being used. It is alsoimportant to verify dosage information and administration.

Known gas delivery devices may include a computerized system fortracking patient information, including information regarding the typeof gas therapy, concentration of gas to be administered and dosageinformation for a particular patient. However, these computerizedsystems often do not communicate with other components of gas deliverydevices, for example, the valve that controls the flow of the gas to thecomputerized system and/or ventilator for administration to the patient.In addition, in known systems, the amount of gas utilized by a singlepatient is often difficult or impossible to discern, leading to possibleoverbilling for usage.

There is a need for a gas delivery device that integrates a computerizedsystem to ensure that patient information contained within thecomputerized system matches the gas that is to be delivered by the gasdelivery device. There is also a need for such an integrated device thatdoes not rely on repeated manual set-ups or connections and which canalso track individual patient usage accurately and simply.

SUMMARY

Aspects of the present invention pertain to a gas delivery device thatmay be utilized with a gas delivery system and methods for administeringtherapy gas to a patient. The therapy gas may comprise nitric oxide(NO). One or more embodiments of the gas delivery devices describedherein may include a valve and a circuit with a valve memory incommunication with a valve processor and a valve transceiver. One ormore embodiments of the gas delivery systems described hereinincorporate the gas delivery devices described herein with a controlmodule including a control processing unit (CPU) in communication with aCPU memory and CPU transceiver. As will be described herein, the valvetransceiver and the CPU transceiver may be in communication such thatinformation or data from the valve memory and the CPU memory may becommunicated to one another. The information communicated between thevalve memory and the CPU memory may be utilized for selecting a therapyfor delivery to a patient and controlling delivery of the selectedtherapy to the patient. The gas delivery devices and systems describedherein may be utilized with medical devices such as ventilators and thelike to delivery gas to a patient.

A first aspect of the present invention pertains to a gas deliverydevice. In one or more embodiments, the gas delivery device administerstherapy gas from a gas source containing NO under the control of acontrol module. The control module may deliver the gas comprising NO toa patient in an amount effective to treat and/or prevent hypoxicrespiratory failure and/or pulmonary hypertension. In one variant, thegas delivery device may include a valve attachable to the gas source anda circuit. The valve may include an inlet and an outlet in fluidcommunication and a valve actuator to open and close the valve to allowthe gas to flow through the valve to a control module. The circuit ofone or more embodiments includes a memory, a processor and a transceiverin communication with the memory to send wireless optical line-of-sightsignals to communicate information stored or retained within the memoryto the control module that controls gas delivery to a subject. In one ormore alternative embodiments, the signals to communicate informationstored or retained within the memory to the control module that controlsgas delivery to a subject may be communicated via a wire. Examples ofsuch wired signals may incorporate or utilize an optical cable, wiredpair and/or coaxial cable. The circuit may include a memory to store gasdata, which may include one or more of gas identification, gasexpiration date and gas concentration. The transceiver may communicateto send the gas data to the control module via wireless opticalline-of-sight signals.

In one or more embodiments, the valve may include a data input incommunication with said memory, to permit a user to enter the gas datainto the memory. The gas data may be provided in a bar code that may bedisposed on the gas source. In such embodiments, the gas data may beentered into the data input of the valve for storage in the memory by auser-operated scanning device in communication with the data input.Specifically, the user may scan the bar code to communicate the gas datastored therein to the valve memory via the data input.

In one or more embodiments, the valve may include a power source. Insuch embodiments, the power source may include a battery or otherportable power source. In one or more embodiments, the valve transceivermay periodically send the wireless optical line-of-sight signals to thecontrol module, wherein the signals are interrupted by a duration oftime at which no signal is sent. In one or more specific embodiments,the duration of time at which no signal is sent comprises about 10seconds.

A second aspect of the present invention pertains to a gas deliverydevice, as described herein, and a control module in fluid communicationwith the outlet of the valve of the gas delivery device and with a gasdelivery mechanism, such as a ventilator. In one or more embodiments,the control module may include a CPU transceiver to receiveline-of-sight signals from the transceiver and a CPU in communicationwith the CPU transceiver. The CPU carries out the instructions of acomputer program or algorithm. As used herein the phrase “wirelessoptical line-of-sight signal” includes infrared signal and other signalsthat require a transmitter and receiver or two transceivers to be inaligned such that the signal may be transmitted in a straight line. TheCPU may include a CPU memory that stores the gas data that iscommunicated by the valve transceiver of the gas delivery device to theCPU transceiver.

In one or more embodiments, the gas delivery system may incorporate avalve with a timer including a calendar timer and an event timer fordetermining or marking the date and time that the valve is opened andclosed and the duration of time the valve is opened. In suchembodiments, the valve memory stores the date and time of opening andclosing of the valve and the duration of time that the valve is open andthe valve transceiver communicates the date and time of opening andclosing of the valve to the CPU transceiver for storage in the CPUmemory.

In one or more variants, the gas delivery system may incorporate acontrol module that further includes an input means to enter patientinformation into the CPU memory. The control module may also have a realtime clock built into the CPU module such that the control module knowswhat the current time and date is and can compare that to the expirationdate stored in the gas delivery device. If the expiration date is passedthe current date then the control module can cause an alarm and notdeliver drug to the patient. When the term “patient information” isused, it is meant to include both patient information entered by theuser and information that is set during manufacturing, such as the gasidentification and the gas concentration that the control module issetup to deliver. The control module may also include a display. In oneor more embodiments, the display incorporates an input means forentering patient information into the CPU memory. In one or moreembodiments, the CPU of the control module compares the patientinformation entered into the CPU memory via the input means and the gasdata from the transceiver. The CPU or control module may includecomprises an alarm that is triggered when the patient informationentered into the CPU memory and the gas data from the transceiver do notmatch or conflict. As used herein the phrase “do not match,” includesthe phrase “are not identical,” “are not substantially identical,” “doconflict” and/or “do substantially conflict.” The CPU determines whetherthe patient information and additional data, or other data set matchesby performing a matching algorithm which includes criteria forestablishing whether one set of data (i.e. patient information) andanother set of data match. The algorithm may be configured to determinea match where every parameter of the data sets match or selectedparameters of the data sets match. The algorithm may be configured toinclude a margin of error. For example, where the patient informationrequire a gas concentration of 800 ppm, and the additional data includesa gas concentration of 805 ppm, the algorithm may be configured toinclude a margin of error of ±5 ppm such it determines that the patientinformation and the additional data match. It will be understood thatdetermining whether the patient information and additional data matchwill vary depending on the circumstances, such as variables in measuringgas concentration due to temperature and pressure considerations.

A third aspect of the present invention pertains to a control modulememory comprising instructions that cause a control module processor toreceive gas data from a valve via a wireless optical line-of-sightsignal. The valve may be connected to a gas source containing NO and mayinclude a memory for storing the gas data. The control module memory mayinclude instructions that cause the control module processor to comparethe gas data with user-inputted patient information. The user-inputtedpatient information may be stored within the control module memory. Gasdata may be selected from one or more of gas identification, gasexpiration date and gas concentration. In one or more embodiments, thecontrol module memory may include instructions to cause the controlmodule processor to coordinate delivery of therapy to the patient with amedical device, such as a ventilator and the like for delivering gas toa patient, via the wireless optical line-of-sight signal. The controlmodule memory may also include instructions to cause the control moduleprocessor to select a therapy for delivery to a patient based on thereceived patient information and control delivery of the selectedtherapy to the patient.

In one or more embodiments, the memory may include instructions to causethe processor to detect the presence of more than one valve and whethermore than one valve is open at the same time. In accordance with one ormore specific embodiments, the memory includes instructions to cause theprocessor to receive a first valve status selected from a first openposition and a first closed position from a first valve via a firstwireless optical line-of-sight signal with the first valve connected toa first gas source, receive a second valve status selected from a secondopen position and a second closed position from a second valve via asecond wireless optical line-of-sight signal with the second valveconnected to a second gas source, compare the first valve status and thesecond valve status, and emit an alarm if the first valve statuscomprises the first open position and the second valve status comprisesthe second open position. In one or more alternative embodiments, thefirst valve status and the second valve status may be communicated tothe processor via a single wireless optical line-of-sight signal,instead of separate wireless optical line-of-sight signals. In a morespecific embodiment, the memory of one or more embodiments may includeinstructions to cause the processor to terminate delivery of therapy ifthe first valve status comprises the first open position and the secondvalve status comprises the second open position.

In one or more embodiments, the memory may include instructions to causethe processor to emit an alarm when a desired dose has been deliveredthrough a valve. In such embodiments, the processor may include a memoryto store the desired dose or dosage information. In such embodiments,the memory may include instructions to cause the processor to receivegas delivery information or information regarding the amount of gasdelivered and compare the gas delivery information to the dosageinformation and emit an alarm when the gas delivery information and thedosage information match. As used herein, the term “dosage information”may be expressed in units of parts per million (ppm), milligrams of thedrug per kilograms of the patient (mg/kg), millimeters per breath, andother units known for measuring and administering a dose. In one or moreembodiments, the dosage information may include various dosage regimeswhich may include administering a standard or constant concentration ofgas to the patient, administering a gas using a pulsed method. Suchpulsing methods includes a method of administering a therapy gas to apatient during an inspiratory cycle of the patient, where the gas isadministered over a single breath or over a plurality of breaths and isdelivery independent of the respiratory pattern of the patient.

A fourth aspect of the present invention pertains to a method foradministering a therapy gas to a patient. The therapy gas may compriseNO. In one or more embodiments, the method includes establishingcommunication between the patient and a gas delivery device via atransceiver, wherein the gas delivery device comprises a first memoryincluding gas data, comparing the gas data with patient informationstored within a second memory. The second memory may be included withina control module in communication with the gas delivery device. Aftercomparing the gas data and the patient information, the method mayfurther include coordinating delivery of therapy to a patient with thegas delivery device via a wireless optical line-of-sight signal,selecting a therapy for delivery to the patient based on the comparisonof the gas data and the patient information and controlling delivery ofthe selected therapy to the patient. In one or more specificembodiments, the method may include entering the gas data into the firstmemory of the gas delivery device and/or entering the patientinformation into the second memory. In embodiments in which the methodincludes entering the patient information into the second memory, thecontrol module may include input means by which patient information maybe entered into the second memory. In one or more variants, the methodincludes ceasing delivery of the selected therapy to the patient basedon the comparison of the gas data and the patient information. Themethod may include emitting an alert based on the comparison of the gasdata and the patient information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a gas delivery system including a gas deliverydevice, a gas source, a control module and a gas delivery mechanism,according to one or more embodiments;

FIG. 2 illustrates a valve assembly of the gas delivery device accordingto one or more embodiments attached to a gas source;

FIG. 3 illustrates a disassembled view of the valve assembly shown inFIG. 2;

FIG. 4 is a diagram showing a circuit supported in the valve assemblyshown in FIG. 2, according to one or more embodiments;

FIG. 5 illustrates an exemplary gas source for use with the valveassembly shown in FIG. 2;

FIG. 6 is an operational flow diagram of the communication between thecircuit of the gas delivery device shown in FIG. 1 with a control moduleregarding the establishment of communication between the circuit and thecontrol module

FIG. 7 illustrates a front view of an exemplary gas delivery system;

FIG. 8 illustrates a back view of the gas delivery system shown in FIG.7;

FIG. 9 illustrates a partial side view of the gas delivery system shownin FIG. 7;

FIG. 10 illustrates a front view of a control module according to one ormore embodiments;

FIG. 11 illustrates a back view of the control module shown in FIG. 10;

FIG. 12 is an operational flow diagram of the communication between thecircuit of the gas delivery device and the control module shown in FIG.1 regarding the gas contained within a gas source; and

FIG. 13 is an operational flow diagram of the preparation of a gasdelivery device and use within the gas delivery system according to oneor more embodiments.

DETAILED DESCRIPTION

Before describing several exemplary embodiments of the invention, it isto be understood that the invention is not limited to the details ofconstruction or process steps set forth in the following description.The invention is capable of other embodiments and of being practiced orbeing carried out in various ways.

A system for the administration of therapy gas is described. A firstaspect of the present invention pertains to a gas delivery device. Thegas delivery device may include a valve assembly including at least onevalve with a circuit. The gas delivery system may include the gasdelivery device (e.g. valve assembly, including a valve and a circuit)in communication with a control module to control the delivery of gasfrom a gas source to a ventilator or other device used to introduce thegas into the patient, for example, a nasal cannula, endotracheal tube,face mask or the like. Gas source, as used herein, may include a gassource, gas tank or other pressured vessel used to store gases at aboveatmospheric pressure. The gas delivery system 10 is shown in FIG. 1. InFIG. 1, the valve assembly 100, including a valve 107 or valve actuatorand a circuit 150, is in communication with a control module 200 via awireless line-of-sight connection 300. In one or more alternativeembodiments, communication between the valve assembly 100 and thecontrol module 200 may be established via a wired signal. The gasdelivery system 10 also includes a gas source 50 including a gasattached to the valve assembly 100 and a gas delivery mechanism, whichincludes a ventilator 400 and a breathing circuit 410, in communicationwith the control module 200.

FIGS. 2-4 illustrate the components of the valve assembly 100. The valveassembly 100 includes a valve 107 and a circuit 150 supported in thevalve assembly. FIG. 3 illustrates a disassembled view of the valveassembly 100, showing components of the physical circuit 150 and thevalve 107. As shown in FIG. 4, which will be described in more detailbelow, the circuit 150 of the gas delivery device includes a valvetransceiver 120 for establishing communication with the control module200, which will also be discussed in greater detail below.

Referring to FIG. 2, the valve 107 includes an attachment portion 102for attaching the valve assembly 100 to the gas source 50, an inlet 104and an outlet 106 in fluid communication with the inlet 104, as moreclearly shown in FIG. 2.

FIG. 3 illustrates a disassembled view of the valve assembly 100 andillustrates an actuator 114 is disposed on the valve 107 and isrotatable around the valve 107 for opening and closing the valve 107.The actuator 114 includes a cap 112 mounted thereto. As shown in FIG. 3,the circuit 150 may include a data input 108 disposed on the actuator114. The data input 108 may be disposed at other locations on the valve107. In one or more variants, the data input may include a port such asa USB port, a receiver for receiving electronic signals from atransmitted or other known input means known in the art for enteringinformation or data into a memory.

FIG. 4 illustrates a block diagram of the circuit 150. The circuit 150shown in FIG. 4 includes a valve processor 122, a valve memory 134, areset 128, a valve transceiver 120 and a power source 130. The circuit150 may also include support circuits a timer 124, a sensor 126 and/orother sensors. Referring to FIG. 3, the circuit 150 is supported withinthe valve assembly 100, with the physical components of the circuit 150specifically disposed between actuator 114 and the cap 112. As shown inFIG. 3, the valve display 132 and the valve transceiver 120 are disposedadjacent to the cap 112, such that the valve display 132 is visiblethrough a window 113. The sensor 126 and the valve processor 122 aredisposed beneath the valve display 132 and the valve transceiver 120,within the actuator 114.

The valve processor 122 may be one of any form of computer processorthat can be used in an industrial setting for controlling variousactions and sub-processors. The valve memory 134, or computer-readablemedium, may be one or more of readily available memory such aselectrically erasable programmable read only memory (EEPROM), randomaccess memory (RAM), read only memory (ROM), floppy disk, hard disk, orany other form of digital storage, local or remote, and is typicallycoupled to the valve processor 122. The support circuits may be coupledto the valve processor 122 for supporting the circuit 150 in aconventional manner. These circuits include cache, power supplies, clockcircuits, input/output circuitry, subsystems, and the like.

In the embodiment shown, the valve memory 134 communicates with a datainput 108 disposed on the side of the actuator 114. The data input 108shown in FIGS. 3-4 is used to transfer data from the valve memory 134 toother devices or to input data into the valve memory 134. For example,gas data, which includes information regarding the gas contained withinthe gas source, may be entered into the valve memory 134 via the datainput 108. In one or more alternative embodiments, the gas data may beprogrammed or directly entered into the valve memory 134 by the gassupplier. In one or more embodiments, the gas data may be provided inthe form of a bar code 610 that is disposed on a label 600 that isaffixed on a to the side of the gas source, as shown in FIG. 5. The barcode 610 may be disposed directly on the gas source. An externalscanning device in communication with the electronic data input 108 maybe provided and may be used to scan the bar code 610 and convey theinformation from the bar code 610 to the valve memory 134. Gas data mayinclude information regarding the gas composition (e.g., NO, O₂, NO₂,CO, etc.), concentration, expiration date, batch and lot number, date ofmanufacturing and other information. Gas data may be configured toinclude one or more types of information. The valve processor 122 mayinclude instructions to convey all or a pre-determined portion of thegas data via the valve transceiver 120 to another transceiver.

In embodiments that utilize a timer 124, the timer 124 may include twosub-timers, one of which is a calendar timer and the other of which isan event timer. The reset 128 may be located inside the actuator 114 andmay be depressed to reset the event timer. The cap 112 also includes awindow 113 that allows the user to see the valve display 132 disposedwithin the cap 112 that displays information regarding whether theactuator 114 is opened or closed and the duration the valve 107 wasopened or closed. In one or more embodiments, the valve display 132 mayalternate flashing of two different numbers, a first number may beaccumulated open time, and the second number may be the time at whichthe valve 107 was opened for the current event. The time at which thevalve 107 was opened for a current event may be preceded by otherindicators.

The sensor 126 disposed within the actuator 114 may include a proximityswitch model MK20-B-100-W manufactured by Meder Inc. The sensor 126utilized in one or more embodiments may cooperate with a magnet (notshown) to sense whether the actuator 114 is turned on or turned off.Such sensors are described in U.S. Pat. No. 7,114,510, which isincorporated by reference in its entirety.

For example, the sensor 126 and a corresponding magnet (not shown) maybe disposed on a stationary portion of the valve 107. When the actuator114 is rotated to the closed position, the sensor 126 is adjacent to themagnet that is in a fixed position on the valve 107. When the sensor 126is adjacent to the magnet, it sends no signal to the valve processor122, thereby indicating that the actuator 114 is in the “closed”position or has a valve status that includes an open position or aclosed position. When the actuator 114 is rotated to open the valve 107,the sensor 126 senses that it has been moved away from the magnet andsends a signal to the valve processor 122, indicating an “open”position. The valve processor 122 instructs the valve memory 134 torecord the event of opening the valve 107 and to record the time anddate of the event as indicated by the calendar timer. The valveprocessor 122 instructs the valve memory 134 to continue checking theposition of the valve 107 as long as the valve 107 is open. When thevalve 107 is closed, the valve processor 122 uses the logged open andclose times to calculate the amount of time the valve 107 was open andinstructs the valve memory 134 to record that duration and theaccumulated open time duration. Thus, every time the valve 107 isopened, the time and date of the event is recorded, the closing time anddate is recorded, the duration of time during which the valve 107 isopen is calculated and recorded, and the accumulated open time iscalculated and recorded.

In one or more embodiments in which the power source 130 includes abattery, the valve transceiver 120 may be configured to communicate withthe CPU transceiver 220 to preserve the life of the battery. In thisembodiment the valve transceiver 120 is only turned on to receive asignal from the Control Module CPU transceiver 220 for 20 msec everysecond. The control module CPU transceiver 220 sends out a shorttransmit signal continuously and if the valve transceiver 120 is presentit responds in the 20 msec interval. This conserves battery power as thevalve transceiver 120 is only powered on for 20 msec every second. Whenthe valve transceiver 120 responds it includes in its signal informationregarding whether the communication from the control module CPUtransceiver 220 was early or late within this 20 msec window. Thisensures that once communications has been established it is synchronizedwith the 20 msec window that the valve transceiver 120 is powered on andable to receive communications. For example, as shown in FIG. 6, thevalve transceiver 120 sends a wireless optical line-of-sight signalduring a pre-determined interval in response to a signal from thecontrol module CPU transceiver 220. The wireless optical line-of-sightsignals sent by the valve transceiver 120 are a series of on off cycleswhere the transmitter is either transmitting light or is not and thesecorrespond to digital binary signals. The mechanism by which the valvetransceiver sends a wireless optical line-of-sight signal may beconstrued as a series of digital on off signals that correspond to databeing transmitted. Once communications has been established between thecontrol module CPU transceiver 220 and the valve transceiver 120, theinterval between communication signals may be in the range from about 20seconds to about 5 seconds. In one or more specific embodiments, theinterval or duration between transceiver signals may be about 10seconds.

As will be described in more detail below, the control module 200includes a CPU 210 which is connected to a CPU transceiver 220 which cansend and receive wireless optical line-of-sight signals. The CPUtransceiver 220 sends out a signal and waits for a response from thevalve transceiver 120 when communication or more specifically,line-of-sight communication is established between the CPU transceiver220 and the valve transceiver 120. If no response is sent by the valvetransceiver 120, the CPU transceiver 220 sends another signal after aperiod of time. This configuration preserves battery life because thevalve transceiver 120 does not continuously send a signal unlessrequested to by the CPU 210. This is important as the gas deliverydevice and gas source spends most of its time in shipping and storageprior to being placed on the gas delivery system, if it was transmittingall this time trying to establish communications with the control moduleit would be consuming the battery life significantly.

The valve processor 122 may include link maintenance instructions todetermine whether the interval should be increased or decreased. Asshown in FIG. 6, when a valid link is established between the valvetransceiver 120 and CPU transceiver 121, the valve processor 122executes the link maintenance instructions to increase the interval ordecrease the interval.

As shown more clearly in FIG. 1, valve assembly 100 and gas source 50 isin communication with a control module 200, which is in communicationwith a gas delivery mechanism. The gas delivery mechanism shown in FIG.1 includes a ventilator 400 with associated breathing circuit 410. Thecontrol module 200 may include a CPU 210 and a CPU transceiver 220 incommunication with the circuit 150 via the valve transceiver 120. Thecontrol module 200 also includes a CPU memory 212 in communication withthe CPU transceiver 220 to store patient information, information ordata received from the valve transceiver 120 and other information. Thecontrol module 200 may also include support circuits. The CPU 210 may beone of any form of computer processor that can be used in an industrialsetting for controlling various actions and sub-processors. The CPUmemory 212, or computer-readable medium, may be one or more of readilyavailable memory such as random access memory (RAM), read only memory(ROM), floppy disk, hard disk, or any other form of digital storage,local or remote, and is typically coupled to the CPU 210. The supportcircuits may be coupled to the CPU 210 for supporting the control module200 in a conventional manner. These circuits include cache, powersupplies, clock circuits, input/output circuitry, subsystems, and thelike. The CPU 210 may also include a speaker 214 for emitting alarms.Alternatively, alarms may also be displayed visually on a display. Asshown in FIG. 1, the control module 200 may also include a regulator 110and, optionally, pressure gauges and flow meters for determining and/orcontrolling the gas flow from the gas source 50.

In one or more embodiments, the CPU transceiver 220 is disposed on acover portion 225 (shown more clearly in FIG. 7), that is part of a cart500 (show more clearly in FIG. 7) onto which the control module 200 isdisposed. The cover portion 225 in one or more embodiments is incommunication with the control module 200. Communication between thecover portion 225 and the control module 200 may be establishedwirelessly or via a cable. As will be discussed in greater detail below,the valve assembly 100, including the valve 107, the circuit 150 and agas source 50 attached to the valve 107, are placed on the cart 500 inproximity and in a light-of-sight path with the CPU transceiver 220.When properly configured such that communication is established betweenthe valve transceiver 120 and the CPU transceiver 220, the CPUtransceiver 220 is positioned directly above the valve transceiver 120,as shown more clearly in FIG. 9. In one or more alternative embodiments,the CPU transceiver 220 may be disposed on the CPU 210.

The CPU 210 may be in communication with a plurality of gas sensors 230for determining the concentration of a sample of gas drawn via a sampleline 232 and a sample line inlet 280 (shown more clearly in FIG. 1)disposed on the control module 200. As will be discussed in greaterdetail, the sample line 232 draws a sample of gas from a breathingcircuit 410 of a ventilator 400 when the ventilator is in fluidcommunication with the control module 200 and gas is being delivered tothe ventilator. The CPU 210 may also be in communication with a sampleflow sensor 234 for sensing the flow of the sample drawn via sample line232, a pump 236 for drawing the sample via the sample line 232 to theflow sensor 234 and zero valve 238 controlling the flow of the samplevia the sample line 232 to the sample pump 236, sample flow sensor 234and the plurality of CPU sensors. The sample line 232 may include awater trap 233 for collecting any water or liquid from the sample.

The control module 200 may also include a delivery module 260 forregulating the flow of gas from the gas source 50 to the ventilator 400.The delivery module 260 may include a pressure switch 262 fordetermining a gas supply pressure is present, a pressure shut-off valve264, a proportional valve 266 and a delivery flow sensor 268. Thedelivery module 260 may also include a backup on/off switch 269. Thedetailed method of how the delivery module delivers the gas to theventilator circuit is described in U.S. Pat. No. 5,558,083 which isincorporated here by reference in its entirety.

The ventilator 400 shown in FIG. 1 is in fluid communication with thecontrol module 200 via an injector tubing 440 and in electricalcommunication via an injector module cable 450. The control module 200and more specifically, the CPU 210, is in fluid communication with theventilator 400 via the sample line 232. The ventilator 400 may include abreathing circuit 410 with an inspiratory limb 412 and an expiratorylimb 414 in fluid communication with the ventilator 400. The inspiratorylimb 412 may be in fluid communication with a humidifier 420, which isin fluid communication with the ventilator 400 via an injector module430. The inspiratory limb 412 carries gas to the patient and theexpiratory limb 414 carries gas exhaled by the patient to the ventilator400. The injector module 430 shown in FIG. 1 is in fluid communicationwith the gas source 50 via the injector tubing 440 and in electroniccommunication with the delivery module 260 via the injector module cable450 such that the delivery module 260 can detect and regulate the flowof gas from the gas source 50 to the ventilator 400. Specifically, theinjector module 430 is in fluid communication with the gas source 50 viaan injector tubing 440, which is in fluid communication with one or moreof the pressure switch 262, pressure shut-off valve 246, proportionalvalve 266, flow sensor 268 and the backup switch 269 of the deliverymodule 260. The injector module 430 may also be in electroniccommunication with the delivery module 260 via the injector module cable450. The inspiratory limb 412 of the ventilator 400 may include a sampletee 416 for facilitating fluid communication between the inspiratorylimb 412 of the breathing circuit and the sample line 232.

As discussed above, the control module 200 may be disposed or attachedon a cart 500, as shown in FIGS. 7-9 to facilitate movement of the gassource 50 and the gas delivery device to a patient in need of gastherapy. The gas source 50 and the valve assembly 100 attached theretomay be placed on the cart 500 in proximity to the control module 200.More specifically, as shown in FIG. 7, the gas source 50 is placed onthe cart 500 such that the valve transceiver 120 is in proximity of theCPU transceiver 220 and a line-of-sight path is established between thevalve transceiver 120 and the CPU transceiver 220. In thisconfiguration, the CPU 210 detects the presence of the circuit 150 andthus the gas source 50 via the CPU transceiver 220.

As shown in FIGS. 7-9, the gas delivery device may include more than onevalve, with each valve being attached to a single gas source. In suchembodiments which utilize a second gas source 60 with a second valveassembly 101, the second valve assembly 101 is positioned in proximityand in a light-of-sight path with a second CPU transceiver as the gassource 60 is loaded onto the cart. The second CPU transceiver 222establishes communication with the second valve assembly 101 and thusdetects the presence of a second gas source 60. In the embodiment shownin FIGS. 7-9, the second CPU transceiver 222 may also be disposed on thecover portion 225 of a cart. In one or more alternative embodiments, thesecond CPU transceiver 222 may be disposed on the CPU 210.

As shown in FIG. 8, the cart 500 may include an optional small bin 510,a mount 512 for supporting the control module 200 on the cart 500, atleast one a holding bracket 520, at least one mounting strap 530, anauxiliary bracket 540, for holding an auxiliary gas source, a pluralityof casters 550 and a caster lock lever 560 disposed on each of theplurality of casters 550. The cart 500 may include a mount 570 formounting the control module 200 on to the cart.

An exemplary control module 200 is shown in FIGS. 10-12 includes adisplay 270 for providing visual indication to the user the componentsof the gas being delivered from the gas source 50 to the ventilator 400(e.g., NO, O₂, NO₂), the concentration of each component and whethercommunication has been established with one or more gas sources. Otherinformation may also be displayed to the user. In addition, visualalarms may also be displayed on the display 270. The control module 200may also include a main power indicator 272 indicating whether thecontrol module is connected to a power source, such as an AC/DC powersource and/or a battery. The control module 200 may also include acontrol wheel 274 allowing the user to navigate through various displaysor information displayed on the display. An injection module tubingoutlet 276 may be disposed on the control module for providing fluidcommunication between the delivery module 260 and the injector module430. An injection module cable port 278 may also be provided on thecontrol module to provide electronic communication between the deliverymodule 260 and the injector module 430. The control module 200 shown inFIGS. 10-12 also includes the sample line inlet 280 in fluidcommunication with the sample line 232 and the inspiratory limb 412 ofthe ventilator 400. In the embodiment shown in FIGS. 10-12, the watertrap 233 is disposed on the control module, adjacent to the sample lineinlet 280.

FIG. 11 illustrates a back view of the control module 200 and shows aplurality of inlets. In the embodiment shown, two gas inlets 282, 284for connecting the control module 200 to the gas source 50 are providedand one auxiliary inlet 286 for connecting the control module 200 to anauxiliary gas source, which may include oxygen or other gas. A powerport 288 is also provided on the back of the control module to connectthe control module to an AC/DC power source.

The control module 200 may also include an input means 290 for allowingthe user to enter patient information, for example the identity of thepatient, the type and concentration of the gas and dose of the gas to beadministered to the patient, the patient's disease or condition to betreated by the gas or reason for treatment, gestational age of thepatient and patient weight. The input means 290 shown in FIG. 12includes a keyboard integrated with the display. In one or morealternative embodiments, the input means may include a USB port or otherport for the connection of an external keyboard or other input mechanismknown in the art. The information entered via the input means 290 isstored within the CPU memory 212.

The control module 200 and the valve assembly 100 may be utilized in thegas delivery system 10 to improve patient safety. Specifically, thesafety benefits of the gas delivery system described herein includedetecting a non-confirming drug or gas source, an expired drug or gas,incorrect gas type, incorrect gas concentration and the like. Inaddition, embodiments of the gas delivery system described herein alsoimprove efficiency of gas therapy.

FIG. 13 is a block diagram showing the sequence of how gas deliverydevice, including the valve assembly 100, may be provided and its usewithin the gas delivery system 10, according to one or more embodiments.As shown in FIG. 13, the gas delivery device 10 is prepared for use byproviding a gas source 50 in the form of a gas cylinder or othercontainer for holding a gas and filling the gas source 50 with a gas(700) and attaching a valve assembly 100 as described herein, toassemble the gas delivery device 10 (710). These steps may be performedby a gas supplier or manufacturer. The gas data regarding the gas filledwithin the gas source 50 is entered into the valve memory 134 asdescribed herein (720). The gas data may be entered into the valvememory 134 by the gas supplier or manufacturer that provides the gassource 50 and assembles the gas delivery device 10. Alternatively, thehospital or other medical facility may enter the gas data into the valvememory 134 after the gas delivery device has been transported to thehospital or medical facility (730). The gas delivery device 10 ispositioned on a cart 500 (740) and communication between the CPUtransceiver 220 and the valve transceiver 120 is established (750). Thegas data stored within the valve memory 134 is conveyed to the controlmodule 200 (760) via the wireless optical line-of-sight communicationbetween valve transceiver 120 and the CPU transceiver 220. The CPU 210compares the gas data to patient information entered into the CPU memory212 (770). The patient information may be entered into the CPU memoryafter the gas data is entered into the CPU memory 212. The patientinformation may be entered into the CPU memory before the gas deliverydevice 10 is positioned in the cart or before communication between theCPU transceiver 220 and the valve transceiver is established. In one ormore alternative embodiments, the patient information may be enteredinto the CPU memory 212 before the gas delivery device 10 is prepared ortransported to the hospital or facility. The CPU 210 then compareswhether the gas data and the patient information match (780). If the gasdata and the patient information match, then gas is administered to thepatient (790), for example through a ventilator or other gas deliverymechanism. If the gas data and the patient information do not match,then an alarm is emitted (800). As described otherwise herein, the alarmmay be audible and emitted through the speaker 214 and/or may be visualand displayed on the display 270.

The gas delivery system described herein simplifies set-up procedures byutilizing wireless line-of-sight signals to establish communication. Theuser does not need to ensure all the cables are correct connected andcan freely load new gas sources onto a cart without disconnecting cableslinking the control module 200 and the valve assembly 100 or circuit150. This reduces set-up time and any time spent correcting errors thatmay have occurred during the set-up process. The control module 200 andthe circuit 150 are further designed to automatically send and detectinformation to establish delivery of a correct gas having the correctconcentration and that is not expired. In one or more specificembodiments, such automated actions prevent the use of the gas deliverysystem by preventing gas flow to a patient, without user intervention.

In one or more embodiments, after communication between the valvetransceiver 120 and the CPU transceiver 220 is established, the valveprocessor 122 includes instructions to convey the gas data stored in thevalve memory 134 via the valve transceiver 120 to the CPU transceiver220. The CPU 210 includes instructions to store the gas data receivedfrom the CPU transceiver 220 in the CPU memory. The CPU 210 alsoincludes an algorithm that compares the gas data with patientinformation that is entered into the CPU memory 212. If the gas data andthe patient information do not match, the CPU 210 includes instructionsto emit an alarm, which may be audible, visual or both, alerting theuser that the gas contained within the gas source is different from thegas to be administered to the patient. For example, as illustrated inFIG. 12, if the gas data includes gas expiration date, the CPU memory212 includes information regarding the current date and the CPU 210compares the gas expiration date with the current date. If the gasexpiration date is earlier than the current date, the CPU 210 emits analarm. The alarm may be emitted through one or both the speaker 214 anddisplay 270. In one or more embodiments, the CPU 210 may includeinstructions that the delivery module 260 cease or prevent delivery ofthe gas. In one or more embodiments, the CPU 210 includes instructionsto turn the backup on/off switch 269 off if the delivery module 260commences or continues delivery of the gas. The detection of an expiredgas by the CPU 210 may be stored within the CPU memory 212.

If the gas data includes gas concentration information or data, the CPUmemory 212 includes information regarding the desired concentration ofgas to be administered to the patient. The control module 200 may beconfigured to alert the user that the gas contained within a gas sourcehas incorrect concentration or a concentration that does not match thedesired gas concentration. For example, a user may enter a concentrationof 800 ppm into the CPU memory 212 and this concentration is compared tothe gas concentration conveyed from the valve memory 134 to the CPUmemory 212. As illustrated in FIG. 12, the CPU 210 includes instructionsto compare the gas concentration of the gas with the concentrationentered by the user. If the gas concentration does not match theconcentration entered by the user, the CPU 210 emits an alarm, which maybe audible and/or visual. In one or more embodiments, the CPU 210 mayinclude instructions that the delivery module 260 cease or preventdelivery of the gas. In one or more embodiments, the CPU 210 includesinstructions to turn the backup on/off switch 269 off if the deliverymodule 260 commences or continues delivery of the gas. The detection ofa gas with incorrect concentration may be stored within the CPU memory212.

In one or more embodiments, the control module 200 may be configured todetect more than one valve and to detect whether more than one valve isturned on. This configuration eliminates waste because it alerts a userthat both valves are turned on and thus unnecessary gas is beingdelivered to via the delivery module 260. In addition, such aconfiguration improves safety because it avoids the issues related tohaving two regulators pressurized at the same time and connected to thedelivery module 260. In one or more embodiments, the cover portion 225of the control module 200 may include a second CPU transceiver 222 andthe CPU 210 may include instructions for the second CPU transceiver 222to detect wireless optical line-of-sight signals from a second valveassembly 101, and more specifically, a second valve transceiver 121. TheCPU 210 may also include instructions that once a second valve assembly101 is detected by the CPU transceiver 222, whether both valveassemblies 100, 101 are opened or have a valve status that includes anopen position. In operation, a first valve assembly 100 includes acircuit with a valve processor with instructions to covey an open orclosed position via the first valve transceiver 120. The circuit of thesecond valve assembly similarly includes a valve processor withinstructions to convey an open or closed position via a second valvetransceiver 121. The first CPU transceiver 220 and the second CPUtransceiver 222 detect the valve statuses for each respective valveassembly from the first valve transceiver 120 and the second valvetransceiver 121 via the wireless optical line-of-sight signals sent byboth transceivers. The CPU 210 instructs the CPU transceivers 220, 222to collect the valve statuses for both valve assemblies 100, 101 and thememory to store the valve statuses. The CPU 210 then compares the valvestatus information from the first valve assembly 100 and the secondvalve assembly 101 and, if the valve statuses both comprise an openposition, the CPU 210 emits an alarm. The alarm may be audible and/orvisual. In one or more embodiments, the CPU 210 may include instructionsthat the delivery module 260 cease or prevent further delivery of gasthrough either the first valve assembly or the second valve assembly. Inone or more embodiments, the CPU 210 includes instructions to turn thebackup on/off switch 269 off if the delivery module 260 commences orcontinues delivery of gas. The detection that more than one valveassembly had a valve that was turned on or had a valve status includingan open position may be stored within the CPU memory.

In one or more embodiments, the control module 200 may be configured toalert a user when the desired dose has been delivered. In suchembodiments, the patient information entered into the CPU memory 212 mayinclude dosage information or the dose to be delivered to a patient. Thevalve processor 122 may include instructions to convey gas usageinformation from the valve memory 134, including the amount of gasdelivered, to the CPU memory 212 via the valve transceiver 120.Alternatively, the valve processor 122 may include instructions to coveythe duration of time the valve 170 has been turned on or has a valvestatus including an open position to the CPU memory 212 via the valvetransceiver 120. The CPU 210 may include instructions to compare thedosage information entered by the user and stored within the CPU memory212 with the gas usage information. The CPU 210 may include instructionsto emit an alarm when the dosage information and the gas usageinformation match. The CPU 210 may include instructions to emit the sameor different alarm to alert the user to turn off the valve or, morespecifically, the actuator 114 when the dose has been delivered. In oneor more embodiments, the CPU 210 may include instructions that thedelivery module 260 cease or prevent further delivery of gas. In one ormore embodiments, the CPU 210 includes instructions to turn the backupon/off switch 269 off if the delivery module 260 commences or continuesdelivery of gas.

In addition, the control module 200 may be configured to alert the userthat a detected valve is and remains closed and no gas is beingdelivered to the patient. This configuration expedites treatment timeand increases efficiency for the hospital. In such embodiments, thevalve processor 122 may include instructions for the valve transceiver120 to convey the valve status to the CPU 210 via a wireless opticalline-of-sight signal. The CPU 210 includes instructions to collect thevalve status information and emit an alert if the dosage information isset or other input has been entered into the CPU memory 212 to commencetreatment and the valve status includes a closed position.

The control module 200 may be configured to alert the user that no valveassembly or gas source has been detected. In such embodiments, the CPU210 includes instructions to detect the presence of a wireless opticalline-of-sight signal from another transceiver, for example, the valvetransceiver 120. The CPU 210 may include instructions to emit an alarmif the dosage information or other input to commence delivery of the gashas been entered into the CPU memory 212 and no signal from anothertransceiver has been detected. Similarly, the control module 200 may beconfigured to emit an alarm if communication between one or both of theCPU transceiver(s) 220, 222 and one or both of the valve transceivers120, 121 has been lost during gas delivery. In such embodiments, the CPU210 may include instructions to continuously detect the presence of asignal from another transceiver and emit an alarm if the dosageinformation or other input to commence delivery of the gas has beenentered into the CPU memory 212 and no signal from another transceiverhas been detected.

The CPU 210 may include instructions to alert a user when sensors in thecontrol module 200 must be calibrated to ensure accurate delivery of gasto a patient. In addition, the CPU 210 may include instructions tocorrelate gas usage information from the circuit 150 of the valveassembly 100 to the patient information entered into the CPU memory 212.The CPU 210 may also have instructions to store the correlated gas usageinformation and the patient information in the CPU memory 212. The valveprocessor 122 may also include instructions detect patient informationfrom the CPU memory 212. Specifically, the valve processor 122 mayinclude instructions to collect patient information via the valvetransceiver 120 from the CPU transceiver 220 and store the collectedpatient information in the valve memory 134. In such embodiments inwhich information from the CPU 210 is collected and stored in the valvememory 134, the CPU 210 may include instructions that the patientinformation and/or correlated patient information and gas usageinformation be conveyed from the CPU memory 212 via the CPU transceiver220 to the valve transceiver 120. The valve processor 122 may alsoinclude instructions to correlate gas usage information with thecollected patient information and store the correlated gas usageinformation and collected patient information in the valve memory 134.Alternatively, the valve processor 122 may include instructions tocollect the correlated patient information and gas usage informationfrom the CPU 210. The correlated information may be utilized to bill theuser according to patient. In addition, the correlated information maybe utilized as patient demographic data, which can assist hospitals orother facilities to generate budget reports, determine usage perdepartment, determine usage per patient diagnosis and link usage ofmultiple gas sources to individual patients.

In one or more embodiments, the gas used for treatment comprises nitricoxide. Nitric oxide relaxes vascular smooth muscle and when inhaled,nitric oxide selectively dilates the pulmonary vasculature, and becauseof efficient scavenging by hemoglobin, has minimal effect on thesystemic vasculature. Accordingly, nitric oxide may be used to treat orprevent pulmonary hypertension and/or hypoxic respiratory failure in apatient by administering an effective amount of a gas comprising nitricoxide. As used herein, a patient refers to a mammal at risk fordeveloping or diagnosed with the referenced disorder. According to oneor more embodiments, the patient is a human. In some embodiments, thepatient may be term or near-term neonate (i.e. >34 weeks).

Nitric oxide is commercially available as INOmax® from Ikaria, Inc.INOmax® is currently indicated for the treatment of term and near-termneonates with hypoxic respiratory failure associated with clinical orechocardiological evidence of pulmonary hypertension.

The gas source may comprise a container having a gas comprising nitricoxide. The nitric oxide may be stored in a carrier gas, such asnitrogen, with a known concentration of nitric oxide. In someembodiments, the nitric concentration in the container may be in therange from 20 ppm to 10,000 ppm or from 100 ppm to 5000 ppm. Exemplarynitric oxide storage concentrations include 100 ppm, 800 pm, 2440 ppmand 4880 ppm. The concentration of nitric oxide delivered to thepatient's lungs may vary depending on the patient or the conditiontreated, but generally may be in the range from 5 ppm to 100 ppm forpreventing or treating various forms of pulmonary hypertension and/orhypoxic respiratory failure. In one or more embodiments, the nitricoxide is delivered at a concentration of about 20 ppm. In someembodiments where the condition being treated or prevented is hypoxicrespiratory failure, the nitric oxide concentration may be delivered ata dose of about 20 ppm.

A second aspect of the present invention pertains to a method foradministering a therapy gas to a patient. The method includes providinga gas in a gas source. The gas source may be prepared by a supplier tocontain a gas having a predetermined composition, concentration andexpiration date. The method may include providing a valve assembly 100attached to a gas source 50 to dispense the gas contained within the gassource 50 to a patient. The method may include entering gas data, whichmay include gas composition, gas concentration and gas expiration date,into the valve memory 134. In one or more embodiments, the supplier mayenter the gas data directly into the valve memory 134. In anothervariant, the gas data is provided in the form of a bar code disposed onthe gas source. In such embodiments, the method includes providing ascanner in communication with the data input 108, scanning the bar codeto collect the gas data information and conveying the gas data to thevalve memory 134 via the data input 108. These steps may be repeated fora second gas source. The gas source(s), with the valve assembly mountedthereon may be transported to a hospital or other facility foradministration to a patient. The gas source(s) are then mounted onto thecart 500 and secured by the holding bracket 520 and mounting strap 530.The method includes establishing communication between the valvetransceivers disposed on each valve and the CPU transceivers 220, 222.Establishing communication may include positioning the valve assembly100 in a line-of-sight path with at least one of the CPU transceivers220, 222. As otherwise described herein, communication may beestablished by instructing the valve transceivers to send a wirelessoptical line-of-sight signal to the CPU transceivers 220, 222. Themethod may include instructing the valve transceiver 120 to send awireless optical line-of-sight signal at pre-determined intervals, asotherwise described herein.

The method may include entering patient information into the CPU memory212. This step may be performed before or after the gas source(s) aremounted onto the cart. The method may specifically include enteringpatient information such as dosage information into the valve memory134. The method includes coordinating delivery of the gas to the patientby collecting gas data from the valve memory 134 and comparing the gasdata with the patient information according to an algorithm anddetermining if the gas data and patient information match, according tothe algorithm. Coordinating delivery of the gas may include turning onthe actuator 114 of the valve 107 such that gas can flow from the inlet104 to the outlet 106. After the dose has been delivered, the method mayinclude correlating the gas usage information and the patientinformation. The method may also include recording the patientinformation, gas usage information and/or the correlated patientinformation and gas usage information in the CPU memory 212 and/or thevalve memory 134. In one or more variants, the method may includeutilizing the patient information, gas usage information and/orcorrelated patient information and gas usage information to generateinvoices identifying the use of the gas by individual patients.

Reference throughout this specification to “one embodiment,” “certainembodiments,” “one or more embodiments” or “an embodiment” means that aparticular feature, structure, material, or characteristic described inconnection with the embodiment is included in at least one embodiment ofthe invention. Thus, the appearances of the phrases such as “in one ormore embodiments,” “in certain embodiments,” “in one embodiment” or “inan embodiment” in various places throughout this specification are notnecessarily referring to the same embodiment of the invention.Furthermore, the particular features, structures, materials, orcharacteristics may be combined in any suitable manner in one or moreembodiments.

Although the invention herein has been described with reference toparticular embodiments, it is to be understood that these embodimentsare merely illustrative of the principles and applications of thepresent invention. It will be apparent to those skilled in the art thatvarious modifications and variations can be made to the method andapparatus of the present invention without departing from the spirit andscope of the invention. Thus, it is intended that the present inventioninclude modifications and variations that are within the scope of theappended claims and their equivalents.

What is claimed is:
 1. A nitric oxide delivery device comprising: acontrol module to deliver a gas comprising NO to a patient in an amounteffective to treat or prevent hypoxic respiratory failure; and a valveassembly to deliver the gas comprising NO from a gas containercontaining the gas comprising NO to the control module, the valveassembly comprising: a valve attachable to the gas container containingthe gas comprising NO, the valve including an inlet and an outlet influid communication and a valve actuator to open or close the valve toallow the gas comprising NO through the valve to the control module; anda circuit supported within the valve assembly and disposed between theactuator and a cap, the circuit including: a valve memory to store gasdata comprising gas concentration in the gas container and a valveprocessor and a valve transceiver in communication with the valve memoryto send wireless optical line-of-sight signals to communicate the gasdata to the control module.
 2. The nitric oxide delivery device of claim1, where in the valve assembly further comprises a data input disposedon the actuator and in communication with said valve memory, to permit auser to enter the gas data into the valve memory.
 3. The nitric oxidedelivery device of claim 2, wherein the gas data is provided in a barcode disposed on the gas container and is entered into the data input bya user-operated scanning device in communication with the data input. 4.The nitric oxide delivery device of claim 1, wherein the valve comprisesa power source; and the valve transceiver periodically sends thewireless optical line-of-sight signals to the control module, whereinthe signals are interrupted by a duration of time at which no signal issent.
 5. The nitric oxide delivery device of claim 4, wherein theduration of time at which no signal is sent comprises about 10 seconds.6. The nitric oxide delivery device of claim 1, wherein the controlmodule comprises: a CPU transceiver to receive line-of-sight signalsfrom the valve transceiver; a CPU in communication with the CPUtransceiver and including a CPU memory; and a display to enter patientinformation into the CPU memory, wherein the valve transceivercommunicates the gas data comprising gas concentration to the CPUtransceiver for storage in the CPU memory, and wherein the CPU comparesthe patient information entered into the CPU memory via the display andthe gas concentration from the valve transceiver.
 7. The nitric oxidedelivery device of claim 6, wherein the valve comprises a timerincluding a calendar timer and an event timer, wherein the valve memorystores the date and time of opening and closing of the valve and theduration of time that the valve is open and the valve transceivercommunicates the date and time of opening and closing of the valve tothe CPU transceiver for storage in the CPU memory.
 8. The nitric oxidedelivery device of claim 6, wherein the CPU comprises an alarm that istriggered when the patient information entered into the CPU memory andthe gas data from the valve transceiver do not match.
 9. The nitricoxide delivery device of claim 6, wherein the CPU memory comprisesinstructions that cause the CPU processor to: receive gas datacomprising gas concentration from the valve via a wireless opticalline-of-sight signal with the valve connected to the gas containercontaining gas comprising NO; compare the gas data with user-inputtedpatient information; coordinate delivery of therapy to the patient witha medical device via the wireless optical line-of-sight signal betweenthe CPU transceiver and the valve transceiver; select a therapy fordelivery to a patient based on the received patient information; andcontrol delivery of the selected therapy to the patient.
 10. The nitricoxide delivery device of claim 9, wherein the memory further comprisesinstructions that cause the CPU processor to: receive a first valvestatus selected from a first open position and a first closed positionfrom a first valve via a first wireless optical line-of-sight signalwith the first valve connected to a first gas container; receive asecond valve status selected from a second open position and a secondclosed position from a second valve via a second wireless opticalline-of-sight signal with the second valve connected to a second gascontainer; compare the first valve status and the second valve status;and emit an alarm if the first valve status comprises the first openposition and the second valve status comprises the second open position.11. The nitric oxide delivery device of claim 10, wherein the memoryfurther comprises instructions that causes the CPU processor to:terminate delivery of therapy if the first valve status comprises thefirst open position and the second valve status comprises the secondopen position.
 12. A method for treating or preventing hypoxicrespiratory failure in a patient, the method comprising: providing thenitric oxide delivery device of claim 6; establishing communicationbetween the valve transceiver and the CPU transceiver and communicatingthe gas data from the valve transceiver to the CPU; comparing the gasdata communicated from the valve transceiver with patient informationstored within the CPU memory; and delivering the gas comprising NO tothe patient in an amount effective to treat or prevent hypoxicrespiratory failure.
 13. The method of claim 12, further comprisingceasing delivery of the gas comprising NO to the patient based on thecomparison of the gas data and the patient information.
 14. The methodof claim 12, further comprising emitting an alert based on thecomparison of the gas data and the patient information.
 15. The methodof claim 12, further comprising entering the gas data into the valvememory.
 16. The method of claim 12, further comprising entering thepatient information into the CPU memory.